Mobile application bar code identification method and system

ABSTRACT

Applicant&#39;s Smartphone application provides ticket-holding patrons an alternative, digital means of verifying personal identification at entry to a venue or event. The Smartphone application periodically generates a unique QR code (barcode) that contains a unique identifier (i.e., mobile device ID) which prompts the venue/event entry system to recognize the patron. No barcode (serving as a ticket, or authentication/verification, or otherwise) is downloaded from the system server to the Smartphone/mobile device client in contrast to prior art systems.

RELATED APPLICATIONS

The following claims the benefit of U.S. Provisional Application No.61/432,673 filed Jan. 14, 2011. The following is also acontinuation-in-part application of U.S. patent application Ser. No.10/320,287 filed on Dec. 16, 2002 which is a continuation of U.S. patentapplication Ser. No. 09/590,455 filed Jun. 9, 2000 (now U.S. Pat. No.6,496,809 issued Dec. 17, 2002).

The teachings of these prior applications are herein incorporated intheir entireties.

BACKGROUND OF THE INVENTION

Common barcode technology is based on a laser emitting diode emitting alaser onto a subject barcode pattern and a reader reading the resultingreflected wave. This technology is unable to read barcodes displayed onPDA/mobile device screens or other liquid crystal displays. See Wu, etal., U.S. Patent Application Publication No. 2004/0035925, publishedFeb. 26, 2004 providing an image processing system for reading barcodesscanned from PDA/cell phone screens.

Yet other systems deliver barcodes to and render the downloaded barcodes on display units of mobile devices. Examples include:

U.S. Pat. No. 6,685,093 to Challa, et al for “System, Method andApparatus for Communicating Information Between a Mobile CommunicationsDevice and a Bar Code Reader”;

U.S. Pat. No. 7,693,744 to Forbes for “Optimised Messages ContainingBarcode Information for Mobile Receiving Devices”; and

U.S. Patent Application Publication No. 2003/0047613 by Funamoto, et al.for “Identification Barcode Assigning Method, Identity Verifying Method,Identification Barcode Assigning Device, Identity Verifying Device andPortable Terminal Device” which generates an identification barcode of acustomer per store or event (i.e., serves as a concert/event ticket).

SUMMARY OF THE INVENTION

With the present invention, Applicant's provide improvements andadvantages over the prior art. In embodiments, the present inventionlocally creates, i.e., generates anew, at the mobile device a barcodedisplay uniquely identifying a person (the holder/bearer of the mobiledevice).

The mobile device may be any of a personal digital assistant (PDA),mobile phone, or other hand held digital processing and/orcommunications device. In a preferred embodiment, the mobile device is aso called smartphone by way of example and not limitation.

Applicant's smartphone application provides ticket-holding patrons analternative, digital means of verifying personal identification at entryto a venue or event. The smartphone application periodically generates aunique QR code (barcode) that contains a unique identifier (i.e., mobiledevice ID) which prompts the venue/event entry system to recognize thepatron. No barcode (serving as a ticket, or otherwise) is downloadedfrom the system server to the smartphone/mobile device client incontrast to prior art systems.

In a preferred embodiment, a computer-based method electronicallyauthenticates a person (e.g., patron) at a venue or event entry, orotherwise. The person may be a patron, especially an account holdingpatron. To that end the method electronically verifies a person as anaccount holding patron/customer and electronically accesses patronaccount. The preferred method includes electronically storing in adatabase an indication of a mobile device user and an indication of acertain mobile device for that user.

The database is operatively coupled to venue or event entry subsystem.The subsystem may include turnstiles and/or gates, especially those thatare electronically controlled and operated.

Next in the preferred embodiment, the method executes a code generatingprogram on the certain mobile device. In turn, the mobile device locallycreates and displays a bar code unique to the mobile device user. Thebar code is not based on data solely driven by the venue or event suchas, location name, address, event title, performance name, eventsession/showing, etc. In this way, the bar code is independent of venuedata and event data.

At the venue or event entry subsystem, the mobile device user displaysthe locally created bar code on the certain mobile device. In response,the method: (a) electronically reads the bar code from the certainmobile device, (b) electronically decodes the bar code into a firstindicator portion indicating mobile device user and a second indicatorportion indicating mobile device, and (c) electronically accesses thedatabase and compares the decoded first indicator portion to thedatabase stored indication of the mobile device user and compares thedecoded second indicator portion to the database stored indication ofthe certain mobile device. Where the comparing results in a match of thefirst indicator portion to the database stored indication of the mobiledevice user and a match of the second indicator portion to the databasestored indication of the certain mobile device, the method automaticallypositively authenticates the mobile device user at the venue or evententry. This may include opening, unlocking or otherwise allowing themobile device user to pass through the gate or turnstile of the venue orevent entry subsystem.

In some embodiments, the database also stores user account information.For each user account, the database stores an indication of one mobiledevice of (associated with) the person (user) holding the account.Restated, per user account, an indication of the mobile device user(person holding the account) is associated with an indication of hiscertain mobile device in the database. Also in embodiments, the databaseper user account, stores ticket information of one or more tickets ownedby the mobile device user (person who holds account). However, the venueor event entry subsystem authenticates identity of the mobile deviceuser as an individual at the venue or event entry separate from andindependent of authenticating him as a specific ticket holder (havingtickets to a specific event).

The locally created bar code uniquely identifies the mobile device userthat is the account holding person/patron/customer. The bar code is notbased on data solely driven by the venue or event such as location name,location address, event title, performer name, event session or showingand the like. Instead the bar code is independent of event data andvenue data.

After positively authenticating the mobile device user at the venue orevent entry, the venue or event entry subsystem further (a) retrievesticket information from the database, and (b) allows or otherwiseenables the authenticated mobile device user to redeem one or moretickets and gain entry to the venue/event.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing will be apparent from the following more particulardescription of example embodiments of the invention, as illustrated inthe accompanying drawings in which like reference characters refer tothe same parts throughout the different views. The drawings are notnecessarily to scale, emphasis instead being placed upon illustratingembodiments of the present invention.

FIG. 1 is a schematic view of a computer network environment in whichembodiments of the present invention are deployed.

FIG. 2 is a block diagram of a computer node of the network of FIG. 1.

FIG. 3 is a schematic diagram of a preferred embodiment.

FIG. 4 is a flow diagram of a venue entry sub system of the FIG. 3embodiment.

DETAILED DESCRIPTION OF THE INVENTION

A description of example embodiments of the invention follows.

The teachings of all patents, published applications and referencescited herein are incorporated by reference in their entirety.

FIG. 1 illustrates a computer network or similar digital processingenvironment in which the present invention may be implemented.

Client computer(s)/mobile devices 50 and server computer(s) 60 provideprocessing, storage, and input/output devices executing applicationprograms and the like. Client computer(s)/devices 50 can also be linkedthrough communications network 70 to other computing devices, includingother client devices/processors 50 and server computer(s) 60. Similarly,other supplemental processing or reading devices 21 may be operativelylinked to server computers 60 through communications network 70.Communications network 70 can be part of a remote access network, aglobal network (e.g., the Internet), a worldwide collection ofcomputers, Local area or Wide area networks, and gateways that currentlyuse respective protocols (TCP/IP, Bluetooth, etc.) to communicate withone another. Other electronic device/computer network architectures aresuitable.

FIG. 2 is a diagram of the internal structure of a computer (e.g.,client processor/device 50 or server computers 60 including supplementaldevices 21) in the computer system 100 of FIG. 1. Each computer 50, 60,21 contains system bus 79, where a bus is a set of hardware lines usedfor data transfer among the components of a computer or processingsystem. Bus 79 is essentially a shared conduit that connects differentelements of a computer system (e.g., processor, disk storage, memory,input/output ports, network ports, etc.) that enables the transfer ofinformation between the elements. Attached to system bus 79 is I/Odevice interface 82 for connecting various input and output devices(e.g., keyboard, mouse, displays, printers, speakers, etc.) to thecomputer 50, 60, 21. Network interface 86 allows the computer to connectto various other devices attached to a network (e.g., network 70 of FIG.1). Memory 90 provides volatile storage for computer softwareinstructions 92 and data 94 used to implement an embodiment of thepresent invention (e.g., mobile device application 15 including QR codegeneration, client/server hashing, database management 31 and supportingcode detailed below). Disk storage 95 provides non-volatile storage forcomputer software instructions 92 and data 94 used to implement anembodiment of the present invention. Central processor unit 84 is alsoattached to system bus 79 and provides for the execution of computerinstructions.

In one embodiment, the processor routines 92 and data 94 are a computerprogram product (generally referenced 92), including a computer readablemedium (e.g., a removable storage medium such as one or more DVD-ROM's,CD-ROM's, diskettes, tapes, non-transient storage, etc.) that providesat least a portion of the software instructions for the inventionsystem. Computer program product 92 can be installed by any suitablesoftware installation procedure, as is well known in the art. In anotherembodiment, at least a portion of the software instructions may also bedownloaded over a cable, communication and/or wireless connection. Inother embodiments, the invention programs are a computer programpropagated signal product 107 embodied on a propagated signal on apropagation medium (e.g., a radio wave, an infrared wave, a laser wave,a sound wave, or an electrical wave propagated over a global networksuch as the Internet, or other network(s)). Such carrier medium orsignals provide at least a portion of the software instructions for thepresent invention routines/program 92.

In alternate embodiments, the propagated signal is an analog carrierwave or digital signal carried on the propagated medium. For example,the propagated signal may be a digitized signal propagated over a globalnetwork (e.g., the Internet), a telecommunications network, or othernetwork. In one embodiment, the propagated signal is a signal that istransmitted over the propagation medium over a period of time, such asthe instructions for a software application sent in packets over anetwork over a period of milliseconds, seconds, minutes, or longer. Inanother embodiment, the computer readable medium of computer programproduct 92 is a propagation medium that the computer system 50 mayreceive and read, such as by receiving the propagation medium andidentifying a propagated signal embodied in the propagation medium, asdescribed above for computer program propagated signal product.

Generally speaking, the term “carrier medium” encompasses the foregoingtransient signals, propagated signals, propagated medium, storagemedium, non-transient medium and the like.

Turning to FIG. 3, a preferred smartphone 50 embodiment is illustrated.It is understood that other mobile devices 50 with similar applicationsprogram 15 are suitable.

Applicant's smartphone application 15 provides ticket-holding patrons analternative, digital means of verifying personal identification at entryto events. The smartphone application 15 periodically generates (locallycreates) a unique QR code 13 (in barcode format) that contains a uniqueidentifier (i.e. Mobile ID) which prompts the system 100 to recognizethe customer.

QR Code Content

The QR code 13 locally created and generated by the mobile application15 contains a unique identifier (or iPhoneMD5 for example) consisting ofthe customer's system Member ID, Mobile ID and Coordinated UniversalTime (UTC) date/time. Application 15 presents (outputs) the QR code 13in barcode format.

At a venue entryway or other electronically controlled (automated) gatesubsystem 23, a scanner/reading device 21 hashes the system Member ID,Mobile ID and UTC date/time information from the QR code (barcode) 13 inthe following manner:MemberID+MobileID+UTCdate/time+Md5Hash[MemberID+MobileID+UTCdate/time]where:

MemberID is a 64 bit integer using the first six digits from acustomer's unique system Member ID (e.g. 999999),

MobileID is a 64 bit integer generated by the system server 60 andcommunicated to mobile application 15 or otherwise input/defined inapplication 15. The Mobile ID is tied directly to the customer's mobiledevice 50 such that the customer can only have one system account tiedto one mobile device (e.g. 9999990000000119). Server 60 stores indatabase 31, per customer, his system Member ID, his correspondingMobile ID and ticket data of his purchased tickets.

UTC date/time is Universal Time and Date (year, month, day followed byhour, minutes, seconds e.g. Aug. 5 2010 14:56:33 encoded as20100805145633). In one embodiment, the mobile application 15 locallygenerates a unique date/time code every 60 seconds. Other frequencies ofdate/time code generation are suitable.

Md5Hash is a one-way encryption of MemberID+MobileID+UTCdate/time.

System 100 Setup

Continuing with FIGS. 1 and 3, database 31 may be a relational or otherconfigured datastore. It is understood that various system and networkarchitectures of mobile devices 50 running application 15, server 60having database 31 and cooperating venue entry subsystems 23, 21 aresuitable. For example, a web server 60 with database 31 supports variousand numerous venues, ticketing agents/distributors, brokers and so onacross plural team sports, entertainment performers and the like,including for example but not limited to ticketing for games, concerts,presentations and live performances. Web server 60 with database 31 maybe remote from venue servers 60 which are local to respective venues.The web server 60 and venue servers 60 (together with venue subsystem 23and reader/scanners 21) may be operatively coupled for communication andprocessing as a WAN (wide area network), LAN (local area network), orother working computer network over a cable network, the Internet, anextranet or the like. Thus, web server 60 and venue servers 60 aregenerically referred to as server 60 herein.

In embodiments, server 60 maintains database 31. As newcustomers/patrons of participating venues become system 100 members,server 60 assigns respective unique system Member ID and records thesame in database 31. As mentioned above, each customer may ‘register’(i.e., indicate to system 100/server 60) one mobile device 50 tocorrespond to or be associated with the customer's system account.Server 60 assigns and records in database 31 a unique Mobile ID for thecustomer (his account). The invention mobile application 15 is thenconfigured or parameterized with the system Member ID (at least thefirst six digits in one embodiment) and the Mobile ID, and ultimatelyinstalled on the customer's subject mobile device 50. To accomplishthis, server 60 may download mobile application 15 so configured andparameterized to subject mobile device 50 through communications network70 or otherwise.

As a customer purchases tickets to events at the various participatingvenues through server 60, system 100/server 60 records the ticket dataaccordingly in database 31 (i.e., tallied under the customer's systemaccount). A “ticket” is a contractual right to attend a venue at acertain date and time or for a certain event. The contractual right maybe to a certain seat or area in the venue or event. To the extent thatan indication of the “ticket” is stored or held electronically, it is an“eticket” or “electronic ticket”. Common or known technology isemployed, and various techniques for displaying such tickets aresuitable.

Venue Entry

A mobile device 50 user runs/executes the invention application program15 on the subject smartphone/mobile device 50. In turn, the executingapplication program 15 generates, or more precisely, locally creates theunique QR code (barcode) 13 and displays the same on the displayscreen/unit of the subject mobile device 50. Step 39 of FIG. 4 isillustrative. Note, server 60 of the system 100 is not responsible forinitially creating this unique bar code 13; mobile device 50 runningapplication 15 is.

At the venue gates or entry subsystem 23, a scanner/reading device 21scans the QR code (barcode) 13 from the mobile device 50 display screen(Step 40, FIG. 4). Scanner/reading device 21 utilizes common or knownbarcode reading technology and is configured to perform the MD5Hash (orsimilar hash) as made clear below.

Once the QR code (barcode) 13 is scanned from the display screen ofmobile device 50, the scanner/reading device 21 in electroniccommunication with server 60 and database 31 employs a series of checksin order to authenticate the user attempting to gain system accountaccess and hence ticket and venue access. The progression of system 100checks is as follows and diagrammed in FIG. 4.

1. Scanner/reader device 21 first decodes the contents of read barcode13 (Step 41). This results in a Member ID candidate value, Mobile IDcandidate value and UTC date/time candidate value.

2. Scanner/reader device 21 checks the UTC date/time candidate value tosee if the read barcode 13 has expired or otherwise meets thresholddate/time ranges as indicated by server 60 (Step 42). If the date/timehas expired, scanner device 21 issues an error message as pertinent.

3. Scanner/reader device 21 in communication with server 60 uses thedecoded results for MobileID candidate value to find System 100 storedcorresponding Member ID in database 31. Known database look up and/ordownload techniques are used (Step 43). Server 60 and/or scanner device21 issues any error message as pertinent if the Mobile ID candidatevalue does not properly index into database 31 or a corresponding MemberID is otherwise unable to be found in database 31.

4. If no errors have been produced up to this stage, then Step 44verifies a hash of read barcode 13 by comparing (a) an MD5 (encrypted)hash of the Member ID candidate value+Mobile ID candidate value+UTCdate/time candidate value to (b) MD5Hash encryption of the system MemberID stored in database 31+corresponding Mobile ID stored in database31+UTC date/time candidate value. This effectively authenticates andverifies the subject mobile device 50 user.

It is understood that Step 44 processing may be performed by and at anycombination of the server 60 and scanner/reader device 21. That is forserver 60 processing Step 44, the server 60 (i) uploads from orotherwise communicates with the scanner/reader device 21 the read anddecoded Member ID candidate value, the Mobile ID candidate value and theUTC date/time candidate value, (ii) utilizes the recently looked-upstored system Member ID and corresponding stored Mobile ID from database31, (iii) executes the hash routine on each set of data values andcompares the two hash results, and (iv) communicates (downloads) theresults of the comparison to scanner/reader device 21. Where thecomparison results in a match, then the user is authenticated (i.e.,system verified).

Alternatively processing may be by or at the scanner/reader device 21(i) requesting database 31 lookup of the stored Mobile ID correspondingto the system Member ID of Step 43 and obtaining (downloading) theresults, and (ii) locally executing the hash routine on the two sets ofdata values (stored and candidate) and making the comparison of hashresults. Where the comparison results in a match, the user isauthenticated (i.e., system verified).

Other configurations of server 60 and/or scanner/reader 21 processing ofStep 44 are suitable.

Where the comparison of hash results do not result in a match, then anerror signal or message is provided by the scanner/reader 21.

5. Once Member ID, i.e., mobile device user authentication, isconfirmed, scanner/reader device 21 and/or server 60 (step 45) check fortickets in the user's account as indicated in database 31. Commondatabase look up using Member ID as an index is employed. Thecorresponding ticket data for this customer/mobile device user (viaMember ID) may be downloaded from server 60 to venue gate subsystem 23or scanner/reader devices 21.

6. Scanner/reader device 21 and/or venue gate subsystem 23 redeemstickets according to the downloaded ticket data (step 46).

Preferably, successful matching of the QR code 13 as read from theuser's mobile device 50 and hashed by the scanner/reader device 21 tothat of the stored data in database 31, as described above, may resultin venue entry and prompts the scanner device 21 or venue entrysubsystem 23 to print the customer's (mobile device 50 user's) seatlocators and/or other ticket data. Unsuccessful matches prompt thescanner/reader device 21 or gate subsystem 23 to deny entry and referthe customer (mobile device user) to the venue box office.

Thus, the locally generated/created barcode 13 at mobile device 50 isnot an “electronic ticket” to an event/venue (does not indicate venueand event) but rather is a digital means of verifying customer identityor authenticating a patron individual (bearer of the mobile device).After authentication of the mobile device user is completed, then system100 considers (retrieves) the pertinent ticket/event data indicated inthe user's system account uniquely tied to/associated with the subjectmobile device 50.

Exemplary

In an example, non-limiting embodiment of system 100, web server 60supports a website for making ticket transactions betweenpatron/customers and ticket agents/distributors/resellers/brokers/venuebox offices and the like, across multiple spectator/team sports and liveperformance-type events. An end user (would be patron/customer) logs onand registers with the website to become a member of system 100. Duringregistration, the end user states his name, address, email address and amobile phone number of his mobile device 50 for example. In turn, server60 creates a user account, assigns a unique Member ID to the end userand assigns a unique Mobile ID for the user indicated mobile device 50.Also, Server 60 creates a record in data base 31 and stores or otherwiseholds therein the newly created user account information (includingpertinent user information), unique Member ID and unique Mobile IDcorresponding to the end user.

Further server 60 configures mobile application 15 for use by the enduser on his mobile device 50. In particular, server 60 sets the MobileID and Member ID parameters in application 15 and downloads theconfigured/parameterized application 15 to end user mobile device 50.The downloading may be accomplished by emailing an application link tothe mobile device 50 or other installation techniques know in the art.The end user mobile device 50 equipped with the application 15 is ableto create as desired (on user command) bar code 13 uniquely identifyingthe end user as the account holding member of system 100, i.e., theregistered member corresponding to the respective account.

As a registered account holding member of system 100, the end user hasaccess to various ticket offerings and sales through website/web server60. In one sample instance, say the end user purchases one or moretickets to an event through the website using a credit card to satisfythe financial aspect of the ticketing transaction. Server 60 recordspertinent ticket data in the database 31 record and account of the enduser indicting for example, event date/time, venue, title/name of theevent, seat/location and amount paid. No paper form of the purchasedticket(s) needs to be mailed, printed from a computer screen display orotherwise provided to the end user.

On the event day/hour, the end user operates (i.e., executes) theapplication 15 on his mobile device 50 and creates bar code 13 on thedisplay unit/screen of device 50. At the venue gate 23, a scanner/reader21 scans and reads barcode 13 from end user mobile device 50.Scanner/reader 21 and/or venue server 60 in communication with webserver 60 and database 31 process the read barcode 13 as described inSteps 40-44 of FIG. 4, and electronically authenticate the end user(i.e., verify his identity as an account holding, registered member ofsystem 100 and not, at this stage, verifying him as a certain ticketholder to the subject event).

Once the end user is authenticated or verified as a system member (not,at this stage, as a subject event ticket holder) by system 100, server60 and scanner/reader 21 access the end user's system account and obtainhis ticket/eticket to the event. This may redeem the ticket/eticket andoperate gate 23 (turnstiles and the like) to allow passage (entry) ofthe end user. Scanner/reader 21, gate 23 or networked printer at thevenue may print a ticket receipt, seat information and the like for theend user.

While this invention has been particularly shown and described withreferences to example embodiments thereof, it will be understood bythose skilled in the art that various changes in form and details may bemade therein without departing from the scope of the inventionencompassed by the appended claims.

What is claimed is:
 1. A computer-implemented method of electronicallyauthenticating a person at a venue or event entry subsystem, comprising:storing, by a server, an application in a memory; receiving, by theserver, a member identification of a user and mobile deviceidentification of a mobile device of the user from the user; modifying,by the server, the application using the received mobile deviceidentification and member identification; transferring, from the server,the modified application to the mobile device of the user; receiving, bythe server, a purchase request of a ticket comprising the memberidentification and mobile device identification from the mobile deviceof the user; associating, by the server, the purchase request with themember identification in a database; receiving, by the server, a quickresponse (QR) code comprising a representation of the memberidentification, the mobile device identification, and a time ofgeneration of the QR code from a scanner device; decoding, by theserver, a QR code using the mobile identification; and comparing, by theserver, a decoded member identification, mobile device identification,and decoded time of generation from the decoded QR code with the ticketassociated with the member identification and mobile deviceidentification in the database; and based on the comparison, sending, bythe server, an authenticating message to the scanner device.
 2. Thecomputer-implemented method of claim 1, further comprising: at themobile device: using the mobile application downloaded from the server,generating the code having the mobile identification, the mobile deviceidentification, and the time.
 3. The method as claimed in claim 1,further comprising: authenticating a person who is an account holdingpatron, the mobile device user being the person holding the account; andwherein the database stores account information, including for eachaccount, an indication of one mobile device associated with the personholding the account.
 4. The method as claimed in claim 3 furthercomprising: storing, per account, ticket information of one or moretickets owned by the user in the database; retrieving ticket informationafter positively authenticating the mobile device user at the venue orevent entry; and allowing the mobile device user to redeem one or moretickets.
 5. The method as claimed in claim 1 wherein the venue or anevent entry subsystem includes a gate or turnstile, the method furthercomprising: automatically positively authenticating the mobile deviceuser by allowing the mobile device user to pass through the gate orturnstile.
 6. The method as claimed in claim 1 wherein the mobile deviceis any of a mobile phone, a PDA, a smartphone and a handheld digitalprocessing device.
 7. The method as claimed in claim 1 wherein theverifying automatically authenticates identity of the mobile device useras an individual at the venue or event entry separate from andindependent of authenticating him as a specific ticket holder.
 8. Themethod as claimed in claim 1 further comprising: after saidauthenticating the mobile device user at the venue or event entry,obtaining from the database ticket data of said user; and redeeming aticket of said user in the database by marking the ticket as used. 9.The method as claimed in claim 1, further comprising determining thecode is valid based on the decoded time of generation being outside ofan expiration time range.
 10. An electronic authentication apparatuselectronically authenticating a person at a venue or event entry,comprising: a server having a memory storing executable instructionsthat when executed by the server causes the server to perform theoperations of: storing an application in the memory; receiving a memberidentification of a user and mobile device identification of a mobiledevice of the user from the user; modifying the application using thereceived mobile device identification and member identification;transferring the modified application to the mobile device of the user;receiving a purchase request of a ticket comprising the memberidentification and mobile device identification from the mobile deviceof the user; associating the purchase request with the memberidentification in a database; receiving a quick response (QR) codecomprising a representation of the member identification, the mobiledevice identification, and a time of generation of the QR code from ascanner device; decoding a QR code using the mobile identification; andcomparing a decoded member identification, mobile device identification,and decoded time of generation from the decoded QR code with the ticketassociated with the member identification and mobile deviceidentification in the database; and based on the comparison, sending anauthenticating message to the scanner device.
 11. The apparatus of claim10, further comprising: a mobile device configured to, using the mobileapplication downloaded from the server, generate the code having themobile identification, the mobile device identification, and the time.12. The apparatus of claim 10, further comprising the memory storingexecutable instructions that when executed by the server causes theserver to perform the operations of: authenticating a person who is anaccount holding patron, the mobile device user being the person holdingthe account; and wherein the database stores account information,including for each account, an indication of one mobile deviceassociated with the person holding the account.
 13. The apparatus ofclaim 12 further comprising comprising the memory storing executableinstructions that when executed by the server causes the server toperform the operations of: storing, per account, ticket information ofone or more tickets owned by the user in the database; retrieving ticketinformation after positively authenticating the mobile device user atthe venue or event entry; and allowing the mobile device user to redeemone or more tickets.
 14. The apparatus of claim 10 wherein the venue oran event entry subsystem includes a gate or turnstile, the serverfurther configured to automatically positively authenticate the mobiledevice user by allowing the mobile device user to pass through the gateor turnstile.
 15. The apparatus of claim 10 wherein the mobile device isany of a mobile phone, a PDA, a smartphone and a handheld digitalprocessing device.
 16. The apparatus of claim 10 wherein the verifyingautomatically authenticates identity of the mobile device user as anindividual at the venue or event entry separate from and independent ofauthenticating him as a specific ticket holder.
 17. The apparatus ofclaim 10, wherein the server is further configured to: after saidauthenticating the mobile device user at the venue or event entry,obtain from the database ticket data of said user; and redeem a ticketof said user in the database by marking the ticket as used.
 18. Theapparatus of claim 10, wherein the server is further configured todetermine the code is valid based on the decoded time being outside ofan expiration time range.
 19. A computer-based electronic authenticationsystem electronically authenticating a person at a venue or event entry,comprising: at a server having a database: a storage means for storingan application in memory; an identification reception means forreceiving a member identification of a user and mobile deviceidentification of a mobile device of the user from the user; anapplication configuration means for modifying the application using thereceived mobile device identification and member identification; atransfer means for transferring the modified application to the mobiledevice of the user; a request reception means for receiving a purchaserequest of a ticket comprising the member identification and mobiledevice identification from the mobile device of the user; an associationmeans for associating the purchase request with the memberidentification in a database; a code reception means for receiving aquick response (QR) code comprising a representation of the memberidentification, the mobile device identification, and a time ofgeneration of the QR code from a scanner device; a decoding means fordecoding a QR code using the mobile identification; and a comparisonmeans for comparing a decoded member identification, mobile deviceidentification, and decoded time of generation from the decoded QR codewith the ticket associated with the member identification and mobiledevice identification in the database; and based on the comparison,sending an authenticating message to the scanner device.